home *** CD-ROM | disk | FTP | other *** search
- alsa-base README.Debian
- -----------------------
-
- contents
- --------
- news
- loading modules
- creating device files
- reloading modules after suspension
- unloading modules
- initscript
-
- news
- ----
- Last updated 3 Feburary 2006
-
-
- loading modules
- ---------------
- Modules are loaded automatically by udev when the hardware is detected
- or inserted.
-
- The /etc/modprobe.d/alsa-base file contains basic configuration entries
- which don't normally need to be customized. The entries may include:
-
- * ALSA autoloader aliases
- * entries that install OSS-emulation and other drivers above drivers
- upon which these depend
- * an entry for each normal sound card driver that will cause a command
- to be executed after the driver has initialized
- * an entry for each abnormal driver (i.e., a driver that drives
- hardware such as a TV card or modem that is not suited to be the
- primary sound card) preventing it from grabbing index 0
-
- Suppose you decide that you need to load a certain driver, snd-foo,
- with options: "dma1=0 ctlport=0x530". The recommended way to set this
- up is to create an additional file in /etc/modprobe.d/ containing an
- "options" line:
-
- # /etc/modprobe.d/alsa_local
- options snd-foo dma1=0 ctlport=0x530
-
-
- creating device files
- ---------------------
- Device files are created automatically by udev when the module is
- loaded, and are located in /dev/snd/. (ALSA's kernel-OSS-emulation
- device files are of course the same as the OSS device files.)
-
-
- reloading modules across APM suspend-and-resume
- -----------------------------------------------
- During suspension many peripherals are switched off; on resuming the
- machine these peripherals need to be re-initialized. Many ALSA
- drivers do this properly but some still do not.
-
- If this problem affects you and if your ALSA drivers are built as
- loadable modules and your kernel supports module unloading then you
- can work around the problem by unloading the driver before suspending
- and loading it again after resuming. This will be done for you
- automatically if you add the name of the problematic sound card driver
- module to the variable force_unload_modules_before_suspend variable in
- /etc/default/alsa. E.g., if your CS46XX and AZX cards don't work
- properly after resuming from APM suspend, add the names of their
- driver modules to the list:
-
- force_unload_modules_before_suspend="snd-cs46xx snd-azx"
-